Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method of transmitting broadcast signals and method of receiving broadcast signals

ABSTRACT

The present invention proposes a method for providing a broadcast content in an apparatus, the method comprising: requesting a filter code to an application running on the apparatus by using a first Application Programming Interface (API); receiving a JavaScript Object Notation (JSON) object from the application in response to the first API; storing the filter code; receiving an Extended File Delivery Table (EFDT) having a first filter code associated with a first file; and selectively downloading the first file by comparing the stored filter code with the first filter code in the EFDT.

This application is a continuation of U.S. application Ser. No.15/821,033, filed on Nov. 22, 2017, now allowed, which claims thebenefit of U.S. Provisional Patent Application No. 62/470,851, filed onMar. 13, 2017 and U.S. Provisional Patent Application No. 62/471,348,filed on Mar. 14, 2017, the contents of which are all herebyincorporated by reference herein in their entirety.

TECHNICAL FIELD

The present invention relates to an apparatus for transmitting broadcastsignals, an apparatus for receiving broadcast signals, a method oftransmitting broadcast signals, and a method of receiving broadcastsignals.

BACKGROUND ART

As analog broadcast signal transmission comes to an end, varioustechnologies for transmitting/receiving digital broadcast signals havebeen developed. A digital broadcast signal may include a larger amountof video/audio data than an analog broadcast signal and further includevarious types of additional data in addition to the video/audio data.

DISCLOSURE Technical Problem

That is, a digital broadcast system can provide high definition (HD)images, multi-channel audio and various additional services. However,data transmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcast.

Technical Solution

According to an object of the present invention, as included herein andbriefly described, the present invention proposes a system foreffectively supporting a next-generation broadcast service in anenvironment that supports next-generation hybrid broadcast using aterrestrial broadcast network and an Internet protocol (IP) network, anda related signaling scheme.

Advantageous Effects

The present invention proposes a method of efficiently providing hybridbroadcast using both a broadcast network and an IP network.

The present invention proposes a method of providing application-basedenhancement based on an application for a basic broadcast service.

The present invention proposes a method of providing application-basedenhancement in synchronization with a broadcast service.

The present invention proposes architecture according to variousprotocols between a primary device (PD) and a companion device (CD), anda communication scheme between applications.

The present invention proposes architecture and a signaling scheme foreffectively delivering information about an electronic service guide(ESG), an emergency alert system (EAS), etc. from a PD side to a CDside.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention, illustrate embodiments of the inventionand together with the description serve to explain the principle of theinvention.

FIG. 1 is a diagram showing a protocol stack according to an embodimentof the present invention.

FIG. 2 is a diagram showing a service discovery procedure according toone embodiment of the present invention.

FIG. 3 is a diagram showing a low level signaling (LLS) table and aservice list table (SLT) according to one embodiment of the presentinvention.

FIG. 4 is a diagram showing a USBD and an S-TSID delivered through ROUTEaccording to one embodiment of the present invention.

FIG. 5 is a diagram showing a USBD delivered through MMT according toone embodiment of the present invention.

FIG. 6 is a diagram showing link layer operation according to oneembodiment of the present invention.

FIG. 7 is a diagram showing a link mapping table (LMT) according to oneembodiment of the present invention.

FIG. 8 illustrates a configuration of a broadcast signal transmissionapparatus for future broadcast services according to an embodiment ofthe present invention.

FIG. 9 illustrates a write operation of a time interleaver according toan embodiment of the present invention.

FIG. 10 illustrates an interlaving address generator including a mainpseudo-random binary sequence (PRBS) generator and a sub-PRBS generatoraccording to each FFT mode which are included in a frequencyinterleavaer according to an embodiment of the present invention.

FIG. 11 is a diagram showing a reception-side broadcast contentprovision apparatus according to an aspect of the present invention.

FIG. 12 is a diagram showing a transmission-side broadcast contentprovision apparatus according to another aspect of the presentinvention.

FIG. 13 is a diagram showing an embodiment of a Get Filter API accordingto the present invention.

FIG. 14 is a diagram showing an example of using a Get Filter APIaccording to the present invention.

FIG. 15 is a diagram showing an embodiment of a Set Filter API accordingto the present invention.

FIG. 16 is a diagram showing an example of using the Set Filter APIaccording to the present invention.

FIG. 17 is a diagram showing an embodiment of a DWD according to thepresent invention.

FIG. 18 is a diagram showing another embodiment of the DWD according tothe present invention.

FIG. 19 is a diagram showing a method of providing broadcast content ata reception side in a reception-side broadcast content provisionapparatus according to the present invention.

BEST MODE

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that may be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although most terms used in the present invention have been selectedfrom general ones widely used in the art, some terms have beenarbitrarily selected by the applicant and their meanings are explainedin detail in the following description as needed. Thus, the presentinvention should be understood based upon the intended meanings of theterms rather than their simple names or meanings.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, aUHDTV service, etc. The present invention may process broadcast signalsfor the future broadcast services through non-MIMO or MIMO according toone embodiment. A non-MIMO scheme according to an embodiment of thepresent invention may include a multiple input single output (MISO)scheme, a single input single output (SISO) scheme, etc. The presentinvention proposes a physical profile (or system) optimized to minimizereceiver complexity while attaining the performance required for aparticular use case.

FIG. 1 is a diagram showing a protocol stack according to an embodimentof the present invention.

A service may be delivered to a receiver through a plurality of layers.First, a transmission side may generate service data. The service datamay be processed for transmission at a delivery layer of thetransmission side and the service data may be encoded into a broadcastsignal and transmitted over a broadcast or broadband network at aphysical layer.

Here, the service data may be generated in an ISO base media file format(BMFF). ISO BMFF media files may be used for broadcast/broadband networkdelivery, media encapsulation and/or synchronization format. Here, theservice data is all data related to the service and may include servicecomponents configuring a linear service, signaling information thereof,non real time (NRT) data and other files.

The delivery layer will be described. The delivery layer may provide afunction for transmitting service data. The service data may bedelivered over a broadcast and/or broadband network.

Broadcast service delivery may include two methods.

As a first method, service data may be processed in media processingunits (MPUs) based on MPEG media transport (MMT) and transmitted usingan MMT protocol (MMTP). In this case, the service data delivered usingthe MMTP may include service components for a linear service and/orservice signaling information thereof.

As a second method, service data may be processed into DASH segments andtransmitted using real time object delivery over unidirectionaltransport (ROUTE), based on MPEG DASH. In this case, the service datadelivered through the ROUTE protocol may include service components fora linear service, service signaling information thereof and/or NRT data.That is, the NRT data and non-timed data such as files may be deliveredthrough ROUTE.

Data processed according to MMTP or ROUTE protocol may be processed intoIP packets through a UDP/IP layer. In service data delivery over thebroadcast network, a service list table (SLT) may also be delivered overthe broadcast network through a UDP/IP layer. The SLT may be deliveredin a low level signaling (LLS) table. The SLT and LLS table will bedescribed later.

IP packets may be processed into link layer packets in a link layer. Thelink layer may encapsulate various formats of data delivered from ahigher layer into link layer packets and then deliver the packets to aphysical layer. The link layer will be described later.

In hybrid service delivery, at least one service element may bedelivered through a broadband path. In hybrid service delivery, datadelivered over broadband may include service components of a DASHformat, service signaling information thereof and/or NRT data. This datamay be processed through HTTP/TCP/IP and delivered to a physical layerfor broadband transmission through a link layer for broadbandtransmission.

The physical layer may process the data received from the delivery layer(higher layer and/or link layer) and transmit the data over thebroadcast or broadband network. A detailed description of the physicallayer will be given later.

The service will be described. The service may be a collection ofservice components displayed to a user, the components may be of variousmedia types, the service may be continuous or intermittent, the servicemay be real time or non real time, and a real-time service may include asequence of TV programs.

The service may have various types. First, the service may be a linearaudio/video or audio service having app based enhancement. Second, theservice may be an app based service, reproduction/configuration of whichis controlled by a downloaded application. Third, the service may be anESG service for providing an electronic service guide (ESG). Fourth, theservice may be an emergency alert (EA) service for providing emergencyalert information.

When a linear service without app based enhancement is delivered overthe broadcast network, the service component may be delivered by (1) oneor more ROUTE sessions or (2) one or more MMTP sessions.

When a linear service having app based enhancement is delivered over thebroadcast network, the service component may be delivered by (1) one ormore ROUTE sessions or (2) zero or more MMTP sessions. In this case,data used for app based enhancement may be delivered through a ROUTEsession in the form of NRT data or other files. In one embodiment of thepresent invention, simultaneous delivery of linear service components(streaming media components) of one service using two protocols may notbe allowed.

When an app based service is delivered over the broadcast network, theservice component may be delivered by one or more ROUTE sessions. Inthis case, the service data used for the app based service may bedelivered through the ROUTE session in the form of NRT data or otherfiles.

Some service components of such a service, some NRT data, files, etc.may be delivered through broadband (hybrid service delivery).

That is, in one embodiment of the present invention, linear servicecomponents of one service may be delivered through the MMT protocol. Inanother embodiment of the present invention, the linear servicecomponents of one service may be delivered through the ROUTE protocol.In another embodiment of the present invention, the linear servicecomponents of one service and NRT data (NRT service components) may bedelivered through the ROUTE protocol. In another embodiment of thepresent invention, the linear service components of one service may bedelivered through the MMT protocol and the NRT data (NRT servicecomponents) may be delivered through the ROUTE protocol. In theabove-described embodiments, some service components of the service orsome NRT data may be delivered through broadband. Here, the app basedservice and data regarding app based enhancement may be delivered overthe broadcast network according to ROUTE or through broadband in theform of NRT data. NRT data may be referred to as locally cached data.

Each ROUTE session includes one or more LCT sessions for wholly orpartially delivering content components configuring the service. Instreaming service delivery, the LCT session may deliver individualcomponents of a user service, such as audio, video or closed captionstream. The streaming media is formatted into a DASH segment.

Each MMTP session includes one or more MMTP packet flows for deliveringall or some of content components or an MMT signaling message. The MMTPpacket flow may deliver a component formatted into MPU or an MMTsignaling message.

For delivery of an NRT user service or system metadata, the LCT sessiondelivers a file based content item. Such content files may includeconsecutive (timed) or discrete (non-timed) media components of the NRTservice or metadata such as service signaling or ESG fragments. Systemmetadata such as service signaling or ESG fragments may be deliveredthrough the signaling message mode of the MMTP.

A receiver may detect a broadcast signal while a tuner tunes tofrequencies. The receiver may extract and send an SLT to a processingmodule. The SLT parser may parse the SLT and acquire and store data in achannel map. The receiver may acquire and deliver bootstrap informationof the SLT to a ROUTE or MMT client. The receiver may acquire and storean SLS. USBD may be acquired and parsed by a signaling parser.

FIG. 2 is a diagram showing a service discovery procedure according toone embodiment of the present invention.

A broadcast stream delivered by a broadcast signal frame of a physicallayer may carry low level signaling (LLS). LLS data may be carriedthrough payload of IP packets delivered to a well-known IP address/port.This LLS may include an SLT according to type thereof. The LLS data maybe formatted in the form of an LLS table. A first byte of every UDP/IPpacket carrying the LLS data may be the start of the LLS table. Unlikethe shown embodiment, an IP stream for delivering the LLS data may bedelivered to a PLP along with other service data.

The SLT may enable the receiver to generate a service list through fastchannel scan and provides access information for locating the SLS. TheSLT includes bootstrap information. This bootstrap information mayenable the receiver to acquire service layer signaling (SLS) of eachservice. When the SLS, that is, service signaling information, isdelivered through ROUTE, the bootstrap information may include an LCTchannel carrying the SLS, a destination IP address of a ROUTE sessionincluding the LCT channel and destination port information. When the SLSis delivered through the MMT, the bootstrap information may include adestination IP address of an MMTP session carrying the SLS anddestination port information.

In the shown embodiment, the SLS of service #1 described in the SLT isdelivered through ROUTE and the SLT may include bootstrap informationsIP1, dIP1 and dPort1 of the ROUTE session including the LCT channeldelivered by the SLS. The SLS of service #2 described in the SLT isdelivered through MMT and the SLT may include bootstrap informationsIP2, dIP2 and dPort2 of the MMTP session including the MMTP packet flowdelivered by the SLS.

The SLS is signaling information describing the properties of theservice and may include receiver capability information forsignificantly reproducing the service or providing information foracquiring the service and the service component of the service. Wheneach service has separate service signaling, the receiver acquiresappropriate SLS for a desired service without parsing all SLSs deliveredwithin a broadcast stream.

When the SLS is delivered through the ROUTE protocol, the SLS may bedelivered through a dedicated LCT channel of a ROUTE session indicatedby the SLT. In some embodiments, this LCT channel may be an LCT channelidentified by tsi=0. In this case, the SLS may include a user servicebundle description (USBD)/user service description (USD), service-basedtransport session instance description (S-TSID) and/or mediapresentation description (MPD).

Here, USBD/USD is one of SLS fragments and may serve as a signaling hubdescribing detailed description information of a service. The USBD mayinclude service identification information, device capabilityinformation, etc. The USBD may include reference information (URIreference) of other SLS fragments (S-TSID, MPD, etc.). That is, theUSBD/USD may reference the S-TSID and the MPD. In addition, the USBD mayfurther include metadata information for enabling the receiver to decidea transmission mode (broadcast/broadband network). A detaileddescription of the USBD/USD will be given below.

The S-TSID is one of SLS fragments and may provide overall sessiondescription information of a transport session carrying the servicecomponent of the service. The S-TSID may provide the ROUTE sessionthrough which the service component of the service is delivered and/ortransport session description information for the LCT channel of theROUTE session. The S-TSID may provide component acquisition informationof service components associated with one service. The S-TSID mayprovide mapping between DASH representation of the MPD and the tsi ofthe service component. The component acquisition information of theS-TSID may be provided in the form of the identifier of the associatedDASH representation and tsi and may or may not include a PLP ID in someembodiments. Through the component acquisition information, the receivermay collect audio/video components of one service and perform bufferingand decoding of DASH media segments. The S-TSID may be referenced by theUSBD as described above. A detailed description of the S-TSID will begiven below.

The MPD is one of SLS fragments and may provide a description of DASHmedia presentation of the service. The MPD may provide a resourceidentifier of media segments and provide context information within themedia presentation of the identified resources. The MPD may describeDASH representation (service component) delivered over the broadcastnetwork and describe additional DASH presentation delivered overbroadband (hybrid delivery). The MPD may be referenced by the USBD asdescribed above.

When the SLS is delivered through the MMT protocol, the SLS may bedelivered through a dedicated MMTP packet flow of the MMTP sessionindicated by the SLT. In some embodiments, the packet_id of the MMTPpackets delivering the SLS may have a value of 00. In this case, the SLSmay include a USBD/USD and/or MMT packet (MP) table.

Here, the USBD is one of SLS fragments and may describe detaileddescription information of a service as in ROUTE. This USBD may includereference information (URI information) of other SLS fragments. The USBDof the MMT may reference an MP table of MMT signaling. In someembodiments, the USBD of the MMT may include reference information ofthe S-TSID and/or the MPD. Here, the S-TSID is for NRT data deliveredthrough the ROUTE protocol. Even when a linear service component isdelivered through the MMT protocol, NRT data may be delivered via theROUTE protocol. The MPD is for a service component delivered overbroadband in hybrid service delivery. The detailed description of theUSBD of the MMT will be given below.

The MP table is a signaling message of the MMT for MPU components andmay provide overall session description information of an MMTP sessioncarrying the service component of the service. In addition, the MP tablemay include a description of an asset delivered through the MMTPsession. The MP table is streaming signaling information for MPUcomponents and may provide a list of assets corresponding to one serviceand location information (component acquisition information) of thesecomponents. The detailed description of the MP table may be defined inthe MMT or modified. Here, the asset is a multimedia data entity, iscombined by one unique ID, and may mean a data entity used to onemultimedia presentation. The asset may correspond to service componentsconfiguring one service. A streaming service component (MPU)corresponding to a desired service may be accessed using the MP table.The MP table may be referenced by the USBD as described above.

The other MMT signaling messages may be defined. Additional informationassociated with the service and the MMTP session may be described bysuch MMT signaling messages.

The ROUTE session is identified by a source IP address, a destination IPaddress and a destination port number. The LCT session is identified bya unique transport session identifier (TSI) within the range of a parentROUTE session. The MMTP session is identified by a destination IPaddress and a destination port number. The MMTP packet flow isidentified by a unique packet_id within the range of a parent MMTPsession.

In case of ROUTE, the S-TSID, the USBD/USD, the MPD or the LCT sessiondelivering the same may be referred to as a service signaling channel.In case of MMTP, the USBD/UD, the MMT signaling message or the packetflow delivering the same may be referred to as a service signalingchannel.

Unlike the shown embodiment, one ROUTE or MMTP session may be deliveredover a plurality of PLPs. That is, one service may be delivered throughone or more PLPs. Unlike the shown embodiment, in some embodiments,components configuring one service may be delivered through differentROUTE sessions. In addition, in some embodiments, components configuringone service may be delivered through different MMTP sessions. In someembodiments, components configuring one service may be divided anddelivered in a ROUTE session and an MMTP session. Although not shown,components configuring one service may be delivered through broadband(hybrid delivery).

FIG. 3 is a diagram showing a low level signaling (LLS) table and aservice list table (SLT) according to one embodiment of the presentinvention.

One embodiment t3010 of the LLS table may include information accordingto an LLS_table_id field, a provider_id field, an LLS_table_versionfield and/or an LLS_table_id field.

The LLS_table_id field may identify the type of the LLS table, and theprovider_id field may identify a service provider associated withservices signaled by the LLS table. Here, the service provider is abroadcaster using all or some of the broadcast streams and theprovider_id field may identify one of a plurality of broadcasters whichis using the broadcast streams. The LLS_table_version field may providethe version information of the LLS table.

According to the value of the LLS_table_id field, the LLS table mayinclude one of the above-described SLT, a rating region table (RRT)including information on a content advisory rating, SystemTimeinformation for providing information associated with a system time, acommon alert protocol (CAP) message for providing information associatedwith emergency alert. In some embodiments, the other information may beincluded in the LLS table.

One embodiment t3020 of the shown SLT may include an @bsid attribute, an@sltCapabilities attribute, an sltInetUrl element and/or a Serviceelement. Each field may be omitted according to the value of the shownUse column or a plurality of fields may be present.

The @bsid attribute may be the identifier of a broadcast stream. The@sltCapabilities attribute may provide capability information requiredto decode and significantly reproduce all services described in the SLT.The sltInetUrl element may provide base URL information used to obtainservice signaling information and ESG for the services of the SLT overbroadband. The sltInetUrl element may further include an @urlTypeattribute, which may indicate the type of data capable of being obtainedthrough the URL.

The Service element may include information on services described in theSLT, and the Service element of each service may be present. The Serviceelement may include an @serviceId attribute, an @sltSvcSeqNum attribute,an @protected attribute, an @majorChannelNo attribute, an@minorChannelNo attribute, an @serviceCategory attribute, an@shortServiceName attribute, an @hidden attribute, an@broadbandAccessRequired attribute, an @svcCapabilities attribute, aBroadcastSvcSignaling element and/or an svcInetUrl element.

The @serviceId attribute is the identifier of the service and the@sltSvcSeqNum attribute may indicate the sequence number of the SLTinformation of the service. The @protected attribute may indicatewhether at least one service component necessary for significantreproduction of the service is protected. The @majorChannelNo attributeand the @minorChannelNo attribute may indicate the major channel numberand minor channel number of the service, respectively.

The @serviceCategory attribute may indicate the category of the service.The category of the service may include a linear A/V service, a linearaudio service, an app based service, an ESG service, an EAS service,etc. The @shortServiceName attribute may provide the short name of theservice. The @hidden attribute may indicate whether the service is fortesting or proprietary use. The @broadbandAccessRequired attribute mayindicate whether broadband access is necessary for significantreproduction of the service. The @svcCapabilities attribute may providecapability information necessary for decoding and significantreproduction of the service.

The BroadcastSvcSignaling element may provide information associatedwith broadcast signaling of the service. This element may provideinformation such as location, protocol and address with respect tosignaling over the broadcast network of the service. Details thereofwill be described below.

The svcInetUrl element may provide URL information for accessing thesignaling information of the service over broadband. The sltInetUrlelement may further include an @urlType attribute, which may indicatethe type of data capable of being obtained through the URL.

The above-described BroadcastSvcSignaling element may include an@slsProtocol attribute, an @slsMajorProtocolVersion attribute, an@slsMinorProtocolVersion attribute, an @slsPlpId attribute, an@slsDestinationIpAddress attribute, an @slsDestinationUdpPort attributeand/or an @slsSourceIpAddress attribute.

The @slsProtocol attribute may indicate the protocol used to deliver theSLS of the service (ROUTE, MMT, etc.). The @slsMajorProtocolVersionattribute and the @slsMinorProtocolVersion attribute may indicate themajor version number and minor version number of the protocol used todeliver the SLS of the service, respectively.

The @slsPlpId attribute may provide a PLP identifier for identifying thePLP delivering the SLS of the service. In some embodiments, this fieldmay be omitted and the PLP information delivered by the SLS may bechecked using a combination of the information of the below-describedLMT and the bootstrap information of the SLT.

The @slsDestinationIpAddress attribute, the @slsDestinationUdpPortattribute and the @slsSourceIpAddress attribute may indicate thedestination IP address, destination UDP port and source IP address ofthe transport packets delivering the SLS of the service, respectively.These may identify the transport session (ROUTE session or MMTP session)delivered by the SLS. These may be included in the bootstrapinformation.

FIG. 4 is a diagram showing a USBD and an S-TSID delivered through ROUTEaccording to one embodiment of the present invention.

One embodiment t4010 of the shown USBD may have a bundleDescription rootelement. The bundleDescription root element may have auserServiceDescription element. The userServiceDescription element maybe an instance of one service.

The userServiceDescription element may include an @globalServiceIDattribute, an @serviceId attribute, an @serviceStatus attribute, an@fullMPDUri attribute, an @sTSIDUri attribute, a name element, aserviceLanguage element, a capabilityCode element and/or adeliveryMethod element. Each field may be omitted according to the valueof the shown Use column or a plurality of fields may be present.

The @globalServiceID attribute is the globally unique identifier of theservice and may be used for link with ESG data(Service@globalServiceID). The @serviceId attribute is a referencecorresponding to the service entry of the SLT and may be equal to theservice ID information of the SLT. The @serviceStatus attribute mayindicate the status of the service. This field may indicate whether theservice is active or inactive.

The @fullMPDUri attribute may reference the MPD fragment of the service.The MPD may provide a reproduction description of a service componentdelivered over the broadcast or broadband network as described above.The @sTSIDUri attribute may reference the S-TSID fragment of theservice. The S-TSID may provide parameters associated with access to thetransport session carrying the service as described above.

The name element may provide the name of the service. This element mayfurther include an @lang attribute and this field may indicate thelanguage of the name provided by the name element. The serviceLanguageelement may indicate available languages of the service. That is, thiselement may arrange the languages capable of being provided by theservice.

The capabilityCode element may indicate capability or capability groupinformation of a receiver necessary to significantly reproduce theservice. This information is compatible with capability informationformat provided in service announcement.

The deliveryMethod element may provide transmission related informationwith respect to content accessed over the broadcast or broadband networkof the service. The deliveryMethod element may include abroadcastAppService element and/or a unicastAppService element. Each ofthese elements may have a basePattern element as a sub element.

The broadcastAppService element may include transmission associatedinformation of the DASH representation delivered over the broadcastnetwork. The DASH representation may include media components over allperiods of the service presentation.

The basePattern element of this element may indicate a character patternused for the receiver to perform matching with the segment URL. This maybe used for a DASH client to request the segments of the representation.Matching may imply delivery of the media segment over the broadcastnetwork.

The unicastAppService element may include transmission relatedinformation of the DASH representation delivered over broadband. TheDASH representation may include media components over all periods of theservice media presentation.

The basePattern element of this element may indicate a character patternused for the receiver to perform matching with the segment URL. This maybe used for a DASH client to request the segments of the representation.Matching may imply delivery of the media segment over broadband.

One embodiment t4020 of the shown S-TSID may have an S-TSID rootelement. The S-TSID root element may include an @serviceId attributeand/or an RS element. Each field may be omitted according to the valueof the shown Use column or a plurality of fields may be present.

The @serviceId attribute is the identifier of the service and mayreference the service of the USBD/USD. The RS element may describeinformation on ROUTE sessions through which the service components ofthe service are delivered. According to the number of ROUTE sessions, aplurality of elements may be present. The RS element may further includean @bsid attribute, an @sIpAddr attribute, an @dIpAddr attribute, an@dport attribute, an @PLPID attribute and/or an LS element.

The @bsid attribute may be the identifier of a broadcast stream in whichthe service components of the service are delivered. If this field isomitted, a default broadcast stream may be a broadcast stream includingthe PLP delivering the SLS of the service. The value of this field maybe equal to that of the @bsid attribute.

The @sIpAddr attribute, the @dIpAddr attribute and the @dport attributemay indicate the source IP address, destination IP address anddestination UDP port of the ROUTE session, respectively. When thesefields are omitted, the default values may be the source address,destination IP address and destination UDP port values of the currentROUTE session delivering the SLS, that is, the S-TSID. This field maynot be omitted in another ROUTE session delivering the servicecomponents of the service, not in the current ROUTE session.

The @PLPID attribute may indicate the PLP ID information of the ROUTEsession. If this field is omitted, the default value may be the PLP IDvalue of the current PLP delivered by the S-TSID. In some embodiments,this field is omitted and the PLP ID information of the ROUTE sessionmay be checked using a combination of the information of thebelow-described LMT and the IP address/UDP port information of the RSelement.

The LS element may describe information on LCT channels through whichthe service components of the service are transmitted. According to thenumber of LCT channel, a plurality of elements may be present. The LSelement may include an @tsi attribute, an @PLPID attribute, an @bwattribute, an @startTime attribute, an @endTime attribute, a SrcFlowelement and/or a RepairFlow element.

The @tsi attribute may indicate the tsi information of the LCT channel.Using this, the LCT channels through which the service components of theservice are delivered may be identified. The @PLPID attribute mayindicate the PLP ID information of the LCT channel. In some embodiments,this field may be omitted. The @bw attribute may indicate the maximumbandwidth of the LCT channel. The @startTime attribute may indicate thestart time of the LCT session and the @endTime attribute may indicatethe end time of the LCT channel.

The SrcFlow element may describe the source flow of ROUTE. The sourceprotocol of ROUTE is used to transmit a delivery object and at least onesource flow may be established within one ROUTE session. The source flowmay deliver associated objects as an object flow.

The RepairFlow element may describe the repair flow of ROUTE. Deliveryobjects delivered according to the source protocol may be protectedaccording to forward error correction (FEC) and the repair protocol maydefine an FEC framework enabling FEC protection.

FIG. 5 is a diagram showing a USBD delivered through MMT according toone embodiment of the present invention.

One embodiment of the shown USBD may have a bundleDescription rootelement. The bundleDescription root element may have auserServiceDescription element. The userServiceDescription element maybe an instance of one service.

The userServiceDescription element may include an @globalServiceIDattribute, an @serviceId attribute, a Name element, a serviceLanguageelement, a contentAdvisoryRating element, a Channel element, ampuComponent element, a routeComponent element, a broadbandComponentelement and/or a ComponentInfo element. Each field may be omittedaccording to the value of the shown Use column or a plurality of fieldsmay be present.

The @globalServiceID attribute, the @serviceId attribute, the Nameelement and/or the serviceLanguage element may be equal to the fields ofthe USBD delivered through ROUTE. The contentAdvisoryRating element mayindicate the content advisory rating of the service. This information iscompatible with content advisory rating information format provided inservice announcement. The Channel element may include informationassociated with the service. A detailed description of this element willbe given below.

The mpuComponent element may provide a description of service componentsdelivered as the MPU of the service. This element may further include an@mmtPackageId attribute and/or an @nextMmtPackageId attribute. The@mmtPackageId attribute may reference the MMT package of the servicecomponents delivered as the MPU of the service. The @nextMmtPackageIdattribute may reference an MMT package to be used after the MMT packagereferenced by the @mmtPackageId attribute in terms of time. Through theinformation of this element, the MP table may be referenced.

The routeComponent element may include a description of the servicecomponents of the service. Even when linear service components aredelivered through the MMT protocol, NRT data may be delivered accordingto the ROUTE protocol as described above. This element may describeinformation on such NRT data. A detailed description of this elementwill be given below.

The broadbandComponent element may include the description of theservice components of the service delivered over broadband. In hybridservice delivery, some service components of one service or other filesmay be delivered over broadband. This element may describe informationon such data. This element may further an @fullMPDUri attribute. Thisattribute may reference the MPD describing the service componentdelivered over broadband. In addition to hybrid service delivery, thebroadcast signal may be weakened due to traveling in a tunnel and thusthis element may be necessary to support handoff between broadband andbroadband. When the broadcast signal is weak, the service component isacquired over broadband and, when the broadcast signal becomes strong,the service component is acquired over the broadcast network to secureservice continuity.

The ComponentInfo element may include information on the servicecomponents of the service. According to the number of service componentsof the service, a plurality of elements may be present. This element maydescribe the type, role, name, identifier or protection of each servicecomponent. Detailed information of this element will be described below.

The above-described Channel element may further include an @serviceGenreattribute, an @serviceIcon attribute and/or a ServiceDescriptionelement. The @serviceGenre attribute may indicate the genre of theservice and the @serviceIcon attribute may include the URL informationof the representative icon of the service. The ServiceDescriptionelement may provide the service description of the service and thiselement may further include an @serviceDescrText attribute and/or an@serviceDescrLang attribute. These attributes may indicate the text ofthe service description and the language used in the text.

The above-described routeComponent element may further include an@sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an@sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute,an @sTSIDMajorProtocolVersion attribute and/or an@sTSIDMinorProtocolVersion attribute.

The @sTSIDUri attribute may reference an S-TSID fragment. This field maybe equal to the field of the USBD delivered through ROUTE. This S-TSIDmay provide access related information of the service componentsdelivered through ROUTE. This S-TSID may be present for NRT datadelivered according to the ROUTE protocol in a state of deliveringlinear service component according to the MMT protocol.

The @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPortattribute and the @sTSIDSourceIpAddress attribute may indicate thedestination IP address, destination UDP port and source IP address ofthe transport packets carrying the above-described S-TSID. That is,these fields may identify the transport session (MMTP session or theROUTE session) carrying the above-described S-TSID.

The @sTSIDMajorProtocolVersion attribute and the@sTSIDMinorProtocolVersion attribute may indicate the major versionnumber and minor version number of the transport protocol used todeliver the above-described S-TSID, respectively.

The above-described ComponentInfo element may further include an@componentType attribute, an @componentRole attribute, an@componentProtectedFlag attribute, an @componentId attribute and/or an@componentName attribute.

The @componentType attribute may indicate the type of the component. Forexample, this attribute may indicate whether the component is an audio,video or closed caption component. The @componentRole attribute mayindicate the role of the component. For example, this attribute mayindicate main audio, music, commentary, etc. if the component is anaudio component. This attribute may indicate primary video if thecomponent is a video component. This attribute may indicate a normalcaption or an easy reader type if the component is a closed captioncomponent.

The @componentProtectedFlag attribute may indicate whether the servicecomponent is protected, for example, encrypted. The @componentIdattribute may indicate the identifier of the service component. Thevalue of this attribute may be the asset_id (asset ID) of the MP tablecorresponding to this service component. The @componentName attributemay indicate the name of the service component.

FIG. 6 is a diagram showing link layer operation according to oneembodiment of the present invention.

The link layer may be a layer between a physical layer and a networklayer. A transmission side may transmit data from the network layer tothe physical layer and a reception side may transmit data from thephysical layer to the network layer (t6010). The purpose of the linklayer is to compress (abstract) all input packet types into one formatfor processing by the physical layer and to secure flexibility andexpandability of an input packet type which is not defined yet. Inaddition, the link layer may provide option for compressing(abstracting) unnecessary information of the header of input packets toefficiently transmit input data. Operation such as overhead reduction,encapsulation, etc. of the link layer is referred to as a link layerprotocol and packets generated using this protocol may be referred to aslink layer packets. The link layer may perform functions such as packetencapsulation, overhead reduction and/or signaling transmission.

At the transmission side, the link layer (ALP) may perform an overheadreduction procedure with respect to input packets and then encapsulatethe input packets into link layer packets. In addition, in someembodiments, the link layer may perform encapsulation into the linklayer packets without performing the overhead reduction procedure. Dueto use of the link layer protocol, data transmission overhead on thephysical layer may be significantly reduced and the link layer protocolaccording to the present invention may provide IP overhead reductionand/or MPEG-2 TS overhead reduction.

When the shown IP packets are input as input packets (t6010), the linklayer may sequentially perform IP header compression, adaptation and/orencapsulation. In some embodiments, some processes may be omitted. Forexample, the RoHC module may perform IP packet header compression toreduce unnecessary overhead. Context information may be extractedthrough the adaptation procedure and transmitted out of band. The IPheader compression and adaption procedure may be collectively referredto as IP header compression. Thereafter, the IP packets may beencapsulated into link layer packets through the encapsulationprocedure.

When MPEG 2 TS packets are input as input packets, the link layer maysequentially perform overhead reduction and/or an encapsulationprocedure with respect to the TS packets. In some embodiments, someprocedures may be omitted. In overhead reduction, the link layer mayprovide sync byte removal, null packet deletion and/or common headerremoval (compression). Through sync byte removal, overhead reduction of1 byte may be provided per TS packet. Null packet deletion may beperformed in a manner in which reinsertion is possible at the receptionside. In addition, deletion (compression) may be performed in a mannerin which common information between consecutive headers may be restoredat the reception side. Some of the overhead reduction procedures may beomitted. Thereafter, through the encapsulation procedure, the TS packetsmay be encapsulated into link layer packets. The link layer packetstructure for encapsulation of the TS packets may be different from thatof the other types of packets.

First, IP header compression will be described.

The IP packets may have a fixed header format but some informationnecessary for a communication environment may be unnecessary for abroadcast environment. The link layer protocol may compress the headerof the IP packet to provide a mechanism for reducing broadcast overhead.

IP header compression may employ a header compressor/decompressor and/oran adaptation module. The IP header compressor (RoHC compressor) mayreduce the size of each IP packet header based on the RoHC scheme.Thereafter, the adaptation module may extract context information andgenerate signaling information from each packet stream. A receiver mayparse signaling information associated with the packet stream and attachcontext information to the packet stream. The RoHC decompressor mayrestore the packet header to reconfigure an original IP packet.Hereinafter, IP header compression may mean only IP header compressionby a header compression or a combination of IP header compression and anadaptation process by an adaptation module. The same is true indecompressing.

Hereinafter, adaptation will be described.

In transmission of a single-direction link, when the receiver does nothave context information, the decompressor cannot restore the receivedpacket header until complete context is received. This may lead tochannel change delay and turn-on delay. Accordingly, through theadaptation function, configuration parameters and context informationbetween the compressor and the decompressor may be transmitted out ofband. The adaptation function may provide construction of link layersignaling using context information and/or configuration parameters. Theadaptation function may use previous configuration parameters and/orcontext information to periodically transmit link layer signalingthrough each physical frame.

Context information is extracted from the compressed IP packets andvarious methods may be used according to adaptation mode.

Mode #1 refers to a mode in which no operation is performed with respectto the compressed packet stream and an adaptation module operates as abuffer.

Mode #2 refers to a mode in which an IR packet is detected from acompressed packet stream to extract context information (static chain).After extraction, the IR packet is converted into an IR-DYN packet andthe IR-DYN packet may be transmitted in the same order within the packetstream in place of an original IR packet.

Mode #3 (t6020) refers to a mode in which IR and IR-DYN packets aredetected from a compressed packet stream to extract context information.A static chain and a dynamic chain may be extracted from the IR packetand a dynamic chain may be extracted from the IR-DYN packet. Afterextraction, the IR and IR-DYN packets are converted into normalcompression packets. The converted packets may be transmitted in thesame order within the packet stream in place of original IR and IR-DYNpackets.

In each mode, the context information is extracted and the remainingpackets may be encapsulated and transmitted according to the link layerpacket structure for the compressed IP packets. The context informationmay be encapsulated and transmitted according to the link layer packetstructure for signaling information, as link layer signaling.

The extracted context information may be included in a RoHC-Udescription table (RDT) and may be transmitted separately from the RoHCpacket flow. Context information may be transmitted through a specificphysical data path along with other signaling information. The specificphysical data path may mean one of normal PLPs, a PLP in which low levelsignaling (LLS) is delivered, a dedicated PLP or an L1 signaling path.Here, the RDT may be context information (static chain and/or dynamicchain) and/or signaling information including information associatedwith header compression. In some embodiments, the RDT shall betransmitted whenever the context information is changed. In addition, insome embodiments, the RDT shall be transmitted every physical frame. Inorder to transmit the RDT every physical frame, the previous RDT may bereused.

The receiver may select a first PLP and first acquire signalinginformation of the SLT, the RDT, the LMT, etc., prior to acquisition ofa packet stream. When signaling information is acquired, the receivermay combine the signaling information to acquire mapping betweenservice—IP information—context information—PLP. That is, the receivermay check which service is transmitted in which IP streams or which IPstreams are delivered in which PLP and acquire context information ofthe PLPs. The receiver may select and decode a PLP carrying a specificpacket stream. The adaptation module may parse context information andcombine the context information with the compressed packets. To thisend, the packet stream may be restored and delivered to the RoHCdecompressor. Thereafter, decompression may start. At this time, thereceiver may detect IR packets to start decompression from an initiallyreceived IR packet (mode 1), detect IR-DYN packets to startdecompression from an initially received IR-DYN packet (mode 2) or startdecompression from any compressed packet (mode 3).

Hereinafter, packet encapsulation will be described.

The link layer protocol may encapsulate all types of input packets suchas IP packets, TS packets, etc. into link layer packets. To this end,the physical layer processes only one packet format independently of theprotocol type of the network layer (here, an MPEG-2 TS packet isconsidered as a network layer packet). Each network layer packet orinput packet is modified into the payload of a generic link layerpacket.

In the packet encapsulation procedure, segmentation may be used. If thenetwork layer packet is too large to be processed in the physical layer,the network layer packet may be segmented into two or more segments. Thelink layer packet header may include fields for segmentation of thetransmission side and recombination of the reception side. Each segmentmay be encapsulated into the link layer packet in the same order as theoriginal location.

In the packet encapsulation procedure, concatenation may also be used.If the network layer packet is sufficiently small such that the payloadof the link layer packet includes several network layer packets,concatenation may be performed. The link layer packet header may includefields for performing concatenation. In concatenation, the input packetsmay be encapsulated into the payload of the link layer packet in thesame order as the original input order.

The link layer packet may include a header and a payload. The header mayinclude a base header, an additional header and/or an optional header.The additional header may be further added according to situation suchas concatenation or segmentation and the additional header may includefields suitable for situations. In addition, for delivery of theadditional information, the optional header may be further included.Each header structure may be pre-defined. As described above, if theinput packets are TS packets, a link layer header having packetsdifferent from the other packets may be used.

Hereinafter, link layer signaling will be described.

Link layer signaling may operate at a level lower than that of the IPlayer. The reception side may acquire link layer signaling faster thanIP level signaling of the LLS, the SLT, the SLS, etc. Accordingly, linklayer signaling may be acquired before session establishment.

Link layer signaling may include internal link layer signaling andexternal link layer signaling. Internal link layer signaling may besignaling information generated at the link layer. This includes theabove-described RDT or the below-described LMT. External link layersignaling may be signaling information received from an external module,an external protocol or a higher layer. The link layer may encapsulatelink layer signaling into a link layer packet and deliver the link layerpacket. A link layer packet structure (header structure) for link layersignaling may be defined and link layer signaling information may beencapsulated according to this structure.

FIG. 7 is a diagram showing a link mapping table (LMT) according to oneembodiment of the present invention.

The LMT may provide a list of higher layer sessions carried through thePLP. In addition, the LMT may provide additional information forprocessing link layer packets carrying the higher layer sessions. Here,the higher layer session may also be referred to as multicast.

Information on IP streams or transport sessions transmitted through aspecific PLP may be acquired through the LMT. In contrast, informationon through which PLP a specific transport session is delivered may beacquired.

The LMT may be delivered in any PLP identified as carrying LLS. Here,the PLP in which the LLS is delivered may be identified by an LLS flagof L1 detail signaling information of a physical layer. The LLS flag maybe a flag field indicating whether the LLS is delivered in the PLP, eachPLP. Here, L1 detail signaling information may correspond to thebelow-described PLS2 data.

That is, the LMT may be delivered in the same PLP along with the LLS.Each LMT shall describe mapping between PLPs and IP addresses/ports asdescribed above. As described above, the LLS may include an SLT and theIP address/port described in the LMT may be any IP address/portassociated with any service described in the SLT delivered in the samePLP as the LMT.

In some embodiments, the PLP identifier information in theabove-described SLT, SLS, etc. may be used to confirm informationindicating through which PLP a specific transport session indicated bythe SLT or SLS is transmitted may be confirmed.

In another embodiment, the PLP identifier information in theabove-described SLT, SLS, etc. will be omitted and PLP information ofthe specific transport session indicated by the SLT or SLS may beconfirmed by referring to the information in the LMT. In this case, thereceiver may combine the LMT and other IP level signaling information toidentify the PLP. Even in this embodiment, the PLP information in theSLT, SLS, etc. is not omitted and may remain in the SLT, SLS, etc.

The LMT according to the shown embodiment may include a signaling_typefield, a PLP_ID field, a num_session field and/or information on eachsession. Although the LMT of the shown embodiment describes IP streamstransmitted through one PLP, a PLP loop may be added to the LMT todescribe information on a plurality of PLPs in some embodiments. In thiscase, the LMT may describe, in a PLP loop, PLPs for any IP address/portassociated with any service described in the SLT delivered together, asdescribed above.

The signaling_type field may indicate the type of signaling informationdelivered by the table. The value of signaling_type field for the LMTmay be set to 0x01. The signaling_type field may be omitted. The PLP_IDfield may identify a target PLP to be described. If the PLP loop isused, each PLP_ID field may identify each target PLP. The PLP_ID fieldand subsequent fields thereof may be included in the PLP loop. Thebelow-described PLP_ID field is an identifier for one PLP of the PLPloop and the below-described fields may be fields for the correspondingPLP.

The num_session field may indicate the number of higher layer sessionsdelivered through the PLP identified by the corresponding PLP_ID field.

According to the number indicated by the num_session field, informationon each session may be included. This information may include asrc_IP_add field, a dst_IP_add field, a src_UDP_port field, adst_UDP_port field, an SID_flag field, a compressed_flag field, an SIDfield and/or a context_id field.

The src_IP_add field, the dst_IP_add field, the src_UDP_port field andthe dst_UDP_port field may indicate the source IP address, thedestination IP address, the source UDP port and the destination UDP portof the transport session among the higher layer sessions deliveredthrough the PLP identified by the corresponding PLP_ID field.

The SID_flag field may indicate whether the link layer packet deliveringthe transport session has an SID field in the optional header. The linklayer packet delivering the higher layer session may have an SID fieldin the optional header and the SID field value may be equal to that ofthe SID field in the LMT.

The compressed_flag field may indicate whether header compression isapplied to the data of the link layer packet delivering the transportsession. In addition, presence/absence of the below-described context_idfield may be determined according to the value of this field. If headercompression is applied (compressed_flag=1), the RDT may be present andthe PLP ID field of the RDT may have the same value as the PLP_ID fieldassociated with this compressed_flag field.

The SID field may indicate the SIDs (sub stream IDs) of the link layerpackets delivering the transport session. These link layer packets mayinclude SIDs having the same values as this SID field in the optionalheader thereof. To this end, the receiver may filter link layer packetsusing LMT information and the SID information of the link layer packetheader, without parsing all link layer packets.

The context_id field may provide a reference for a context id (CID) inthe RDT. The CID information of the RDT may indicate the context ID ofthe compression IP packet stream. The RDT may provide contextinformation of the compression IP packet stream. Through this field, theRDT and the LMT may be associated.

In the above-described embodiments of the signaling information/table ofthe present invention, the fields, elements or attributes may be omittedor may be replaced with other fields. In some embodiments, additionalfields, elements or attributes may be added.

In one embodiment of the present invention, service components of oneservice may be delivered through a plurality of ROUTE sessions. In thiscase, an SLS may be acquired through bootstrap information of an SLT. AnS-TSID and an MPD may be referenced through the USBD of the SLS. TheS-TSID may describe not only the ROUTE session delivered by the SLS butalso transport session description information of another ROUTE sessioncarried by the service components. To this end, the service componentsdelivered through the plurality of ROUTE sessions may all be collected.This is similarly applicable to the case in which the service componentsof one service are delivered through a plurality of MMTP sessions. Forreference, one service component may be simultaneously used by theplurality of services.

In another embodiment of the present invention, bootstrapping of an ESGservice may be performed by a broadcast or broadband network. Byacquiring the ESG over broadband, URL information of the SLT may beused. ESG information may be requested using this URL.

In another embodiment of the present invention, one service component ofone service may be delivered over the broadcast network and the otherservice component may be delivered over broadband (hybrid). The S-TSIDmay describe components delivered over the broadcast network such thatthe ROUTE client acquires desired service components. In addition, theUSBD may have base pattern information to describe which segments (whichcomponents) are delivered through which path. Accordingly, the receivercan confirm a segment to be requested from the broadband service and asegment to be detected in a broadcast stream.

In another embodiment of the present invention, scalable coding of aservice may be performed. The USBD may have all capability informationnecessary to render the service. For example, when one service isprovided in HD or UHD, the capability information of the USBD may have avalue of “HD or UHD”. The receiver may check which component isreproduced in order to render the UHD or HD service using the MPD.

In another embodiment of the present invention, through a TOI field ofthe LCT packets delivered through the LCT channel delivering the SLS,which SLS fragment is delivered using the LCT packets (USBD, S-TSID,MPD, etc.) may be identified.

In another embodiment of the present invention, app components to beused for app based enhancement/an app based service may be deliveredover the broadcast network as NRT components or may be delivered overbroadband. In addition, app signaling for app based enhancement may beperformed by an application signaling table (AST) delivered along withthe SLS. In addition, an event which is signaling for operation to beperformed by the app may be delivered in the form of an event messagetable (EMT) along with the SLS, may be signaled in the MPD or may bein-band signaled in the form of a box within DASH representation. TheAST, the EMT, etc. may be delivered over broadband. App basedenhancement, etc. may be provided using the collected app components andsuch signaling information.

In another embodiment of the present invention, a CAP message may beincluded and provided in the above-described LLS table for emergencyalert. Rich media content for emergency alert may also be provided. Richmedia may be signaled by a CAP message and, if rich media is present,the rich media may be provided as an EAS service signaled by the SLT.

In another embodiment of the present invention, linear servicecomponents may be delivered over the broadcast network according to theMMT protocol. In this case, NRT data (e.g., app components) of theservice may be delivered over the broadcast network according to theROUTE protocol. In addition, the data of the service may be deliveredover broadband. The receiver may access the MMTP session delivering theSLS using the bootstrap information of the SLT. The USBD of the SLSaccording to the MMT may reference the MP table such that the receiveracquires linear service components formatted into the MPU deliveredaccording to the MMT protocol. In addition, the USBD may furtherreference the S-TSID such that the receiver acquires NRT data deliveredaccording to the ROUTE protocol. In addition, the USBD may furtherreference the MPD to provide a reproduction description of datadelivered over broadband.

In another embodiment of the present invention, the receiver may deliverlocation URL information capable of acquiring a file content item (file,etc.) and/or a streaming component to a companion device through a websocket method. The application of the companion device may acquirecomponents, data, etc. through a request through HTTP GET using thisURL. In addition, the receiver may deliver information such as systemtime information, emergency alert information, etc. to the companiondevice.

FIG. 8 illustrates a configuration of a broadcast signal transmissionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal transmission apparatus for future broadcastservices according to the present embodiment may include an inputformatting block 1000, a bit interleaved coding & modulation (BICM)block 1010, a frame building block 1020, an OFDM generation block 1030and a signaling generation block 1040. Description will be given of anoperation of each block of the broadcast signal transmission apparatus.

In input data according to an embodiment of the present invention, IPstream/packets and MPEG2-TS may be main input formats, and other streamtypes are handled as general streams.

The input formatting block 1000 may demultiplex each input stream intoone or a plurality of data pipes, to each of which independent codingand modulation are applied. A DP is the basic unit for robustnesscontrol, which affects QoS. One or a plurality of services or servicecomponents may be carried by one DP. The DP is a logical channel in aphysical layer for delivering service data or related metadata capableof carrying one or a plurality of services or service components.

Since QoS depends on characteristics of a service provided by thebroadcast signal transmission apparatus for future broadcast servicesaccording to the embodiment of the present invention, data correspondingto respective services needs to be processed using different schemes.

BICM block 1010 may include a processing block for a profile (or system)to which MIMO is not applied, and a processing block for a profile (orsystem) to which MIMO is applied and may comprise a plurality blocks forprocessing each Data Pipe.

A processing block of the BICM block to which MIMO is not applied mayinclude a data FEC encoder, a bit interleaver, a constellation mapper, asignal space diversity (SSD) encoding block and a time interleaver. Aprocessing block of the BICM block to which MIMO is applied may isdistinguished from the processing block of the BICM block to which MIMOis not applied in that the processing block further includes a cell-worddemultiplexer and a MIMO encoding block The data FEC encoder performsFEC encoding on an input BBF to generate FECBLOCK procedure using outercoding (BCH) and inner coding (LDPC). The outer coding (BCH) is optionalcoding method. The bit interleaver may interleave outputs of the dataFEC encoder to achieve optimized performance with a combination of LDPCcodes and a modulation scheme while providing an efficientlyimplementable structure. A detailed operation of the bit interleaverwill be described later.

The constellation mapper may modulate each cell word from the bitinterleaver or the cell-word demultiplexer in the advanced profile usingeither QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, or NUQ-1024) ornon-uniform constellation (NUC-16, NUC-64, NUC-256, or NUC-1024) mappingto give a power-normalized constellation point. This constellationmapping is applied only for DPs. It is observed that QAM-16 and NUQs aresquare shaped, while NUCs have arbitrary shapes. Both NUQs and NUCs aredefined specifically for each code rate and the particular one used issignaled by the parameter DP_MOD field in the PLS2 data. The timeinterleaver may operates at a DP level. Parameters of time interleaving(TI) may be set differently for each DP. The time interleaver accordingto an embodiment of the present invention can be positioned between aBICM chain block and a frame builder.

Here, The time interleaver according to an embodiment of the presentinvention can use both a convolutional interleaver (CI) and a blockinterleaver (BI) or selectively using either the CI or the BI accordingto a physical layer pipe (PLP) mode. A PLP according to an embodiment ofthe present invention is a physical path corresponding to the sameconcept as that of the above-described DP, and a name of the PLP may bechanged by a designer. A PLP mode according to an embodiment of thepresent invention may include a single PLP mode or a multi-PLP modeaccording to the number of PLPs processed by a broadcast signaltransmitter or a broadcast signal transmission apparatus. In the presentinvention, time interleaving in which different time interleavingschemes are applied according to PLP modes may be referred to as hybridtime interleaving.

The hybrid time interleaver may include a BI and a CI. That is, whenPLP_NUM=1, the BI is not applied (BI is turned OFF) and only the CI isapplied. When PLP_NUM>1, both the BI and the CI may be applied (BI isturned ON). A structure and an operation of the CI applied whenPLP_NUM>1 may be different from a case of PLP_NUM=1. The hybrid timedeinterleaver may perform an operation corresponding to an inverseoperation of the hybrid time interleaver described above.

The cell-word demultiplexer is used for dividing a single cell-wordstream into dual cell-word streams for MIMO processing. The MIMOencoding block may process an output of the cell-word demultiplexerusing a MIMO encoding scheme. The MIMO encoding scheme of the presentinvention may be defined as full-rate spatial multiplexing (FR-SM) toprovide capacity increase with relatively small complexity increase atthe receiver side. MIMO processing is applied at the DP level. NUQ(e_(1,i) and e_(2,i)) corresponding to a pair of constellation mapperoutputs is fed to an input of a MIMO encoder and paired MIMO encoderoutput (g1,i and g2,i) is transmitted by the same carrier k and OFDMsymbol I of respective TX antennas thereof.

The frame building block 1020 may map the data cells of the input DPsinto the OFDM symbols within a frame, and perform frequency interleavingfor frequency-domain diversity.

A frame according to an embodiment of the present invention is furtherdivided into a preamble, one or more frame signaling symbols (FSSs),normal data symbols. The preamble provides a set of basic transmissionparameters for efficient transmission and reception of a signal. And thepreamble indicates whether the emergency alert service (EAS) is providedin a current frame or not. A main purpose of the FSS is to carry PLSdata. For fast synchronization and channel estimation, and hence fastdecoding of PLS data, the FSS has a dense pilot pattern than a normaldata symbol.

The frame building block 1020 may include a delay compensation block foradjusting timing between DPs and corresponding PLS data to ensure thatthe DPs and the corresponding PLS data are co-timed at a transmitterside, a cell mapper for mapping PLS, DPs, auxiliary streams, dummycells, etc. to active carriers of the OFDM symbols in the frame and afrequency interleaver.

The frequency interleaver may randomly interleave data cells receivedfrom the cell mapper to provide frequency diversity. In addition, thefrequency interleaver may operate on data corresponding to an OFDMsymbol pair including two sequential OFDM symbols or an OFDM symbolusing a different interleaving-seed order to obtain maximum interleavinggain in a single frame.

The OFDM generation block 1030 modulates OFDM carriers by cells producedby the frame building block, inserts pilots, and produces a time domainsignal for transmission. In addition, this block subsequently insertsguard intervals, and applies peak-to-average power ratio (PAPR)reduction processing to produce a final RF signal.

The signaling generation block 1040 may create physical layer signalinginformation used for an operation of each functional block. Signalinginformation according to an embodiment of the present invention mayinclude PLS data. The PLS data includes PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in an FSS symbol in aframe having a fixed size, coding and modulation, which carries basicinformation about the system in addition to the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable reception anddecoding of the PLS2 data. In addition, the PLS1 data remains constantfor the duration of a frame group.

The PLS2 data is a second set of PLS data transmitted in an FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode a desired DP. The PLS2 signaling further includes twotypes of parameters, PLS2 static data (PLS2-STAT data) and PLS2 dynamicdata (PLS2-DYN data). The PLS2 static data is PLS2 data that remainsstatic for the duration of a frame group and the PLS2 dynamic data isPLS2 data that dynamically changes frame by frame.

PLS2 data can include FIC_flag information. FIC (fast informationchannel) is a dedicated channel for carrying cross-layer information toenable fast service acquisition and channel scanning. FIC_FLAG is a1-bit field and indicates whether the FIC is used in a current frame. Ifthis field is set to ‘1’, the FIC is provided in the current frame. Ifthis field set to ‘0’, the FIC is not carried in the current frame.

The BICM block 1010 may include BICM block for protection of the PLSdata including a PLS FEC encoder, a bit interleaver and a constellationmapper.

The PLS FEC encoder may include a scrambler for scrambling PLS1 data andPLS2 data, a BCH encoding/zero insertion block for outer encoding on thescrambled PLS 1,2 data using a shortened BCH code for PLS protection,and insert zero bits after BCH encoding, an LDPC encoding block for LDPCencoding using an LDPC code and an LDPC parity puncturing block. The bitinterleaver may interleave each of shortened and punctured PLS1 data andPLS2 data. The constellation mapper may map the bit-ineterlaeved PLS1data and PLS2 data to constellations.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may correspond tothe broadcast signal transmission apparatus for future broadcastservices described with reference to FIG. 8.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may include asynchronization & demodulation module carrying out demodulationcorresponding to a reverse procedure of a procedure performed by thebroadcast signal transmission apparatus, a frame parsing module parsinginput signal frames and extracting data through which a service selectedby a user is transmitted, a demapping & decoding module which convertinput signals into bit domain data and then deinterleave the same asnecessary, perform demapping of mapping applied for transmissionefficiency and correct an error generated on a transmission channelthrough decoding, an output processor performing reverse procedures ofvarious compression/signal processing procedures which are applied bythe broadcast signal transmission apparatus and a signaling decodingmodule obtaining PLS information from a signal demodulated by thesynchronization & demodulation module.

The frame parsing module, the demapping & decoding module and the outputprocessor may execute functions thereof using data output from thesignaling decoding module.

According to an embodiment of the present invention, each TI group iseither mapped directly to one frame or spread over P_(I) frames. Each TIgroup is also divided into more than one TI block (N_(TI)), where eachTI block corresponds to one usage of a time interleaver memory. The TIblocks within the TI group may contain slightly different numbers ofXFECBLOCKs. Typically, the time interleaver may also function as abuffer for DP data prior to a process of frame building.

The Time interleaving according to an embodiment of the presentinvention is a twisted row-column block interleaver. The twistedrow-column block interleaver according to an embodiment of the presentinvention may column-wise write a first XFECBLOCK into a first column ofa TI memory, and a second XFECBLOCK into a next column, and so on).Then, in an interleaving array, cells are diagonal-wise readdiagonal-wise from a first row (rightwards along a row beginning with aleft-most column) to a last row, N_(r) cells are read out

Moreover, in order to achieve single-memory deinterleaving at a receiverside regardless of a number of XFECBLOCKs in a TI block the twistedrow-column block interleaver may insert the virtual XFECBLOCKs into theTI memory. The virtual XFECBLOCKs must be inserted in front of otherFECBLOCKS to achieve single-memory deinterleaving at a receiver side.

FIG. 9 illustrates a write operation of a time interleaver according toan embodiment of the present invention.

A left block in the figure illustrates a TI memory address array, andright blocks in the figure illustrate a write operation when two virtualFEC blocks and one virtual FEC block are inserted into heads of twocontiguous TI groups, respectively.

The frequency interleaver according to the present embodiment mayinclude an interleaving address generator for generating an interleavingaddress for applying corresponding data to a symbol pair.

FIG. 10 illustrates an interlaving address generator including a mainpseudo-random binary sequence (PRBS) generator and a sub-PRBS generatoraccording to each FFT mode which are included in a frequencyinterleavaer according to an embodiment of the present invention. (a)shows the block diagrams of the interleaving-address generator for 8KFFT mode, (b) shows the block diagrams of the interleaving-addressgenerator for 16K FFT mode and (c) shows the block diagrams of theinterleaving-address generator for 32K FFT mode.

The interleaving process for the OFDM symbol pair is described asfollows, exploiting a single interleaving-sequence. First, availabledata cells (the output cells from the Cell Mapper) to be interleaved inone OFDM symbol O_(m,l) is defined as O_(m,l)=[x_(m,l,0), . . . ,x_(m,l,p), . . . , x_(m,l,Ndata−1)] for l=0, . . . , N_(sym)−1, wherex_(m,l,p) is the p^(th) cell of the l^(th) OFDM symbol in the m^(th)frame and N_(data) is the number of data cells: N_(data)=C_(FSS) for theframe signaling symbol(s), N_(data)=C_(data) for the normal data, andN_(data)=C_(FES) for the frame edge symbol. In addition, the interleaveddata cells are defined as P_(m,l)=[v_(m,l,0), . . . , v_(m,l,Ndata−1)]for l=0, . . . , N_(sym)−1.

For the OFDM symbol pair, the interleaved OFDM symbol pair is given by

v_(m,l,Hi(p))=x_(m,l,p), p=0, . . . , N_(data)−1 for the first OFDMsymbol of each pair

v_(m,l,p)=x_(m,l,Hi(p)), p=0, . . . , N_(data)−1 for the second OFDMsymbol of each pair,

where H_(l)(p) is the interleaving address generated based on a PRBSgenerator and a cyclic shift value (symbol offset) of a sub-PRBSgenerator.

FIG. 11 is a diagram showing a reception-side broadcast contentprovision apparatus according to an aspect of the present invention.

According to an aspect, the present invention may be related to areception-side broadcast content provision apparatus. The reception-sidebroadcast content provision apparatus may provide personalized broadcastcontent using a filter code.

Specifically, the reception-side broadcast content provision apparatusmay acquire a filter code from an application using an API, compare theacquired filter code with a filter code in signaling information todetermine whether broadcast content data related to the signaling datais received, and selectively receive the broadcast content data.

The reception-side broadcast content provision apparatus according tothe present invention may include a tuner and/or a processor.

The processor may request a filter code from an application launched inthe reception-side broadcast content provision apparatus. In addition,the processor may receive (acquire) the filter code from the applicationand store the filter code in the broadcast content provision apparatus.In addition, the processor may compare the filter code in the signalinginformation with the stored filter code and determine whether broadcastcontent data associated with the filter code in the signalinginformation is downloaded (received) or not.

The tuner may receive signaling information. This signaling informationmay include an EFDT (Extended File Delivery Table). In addition, thetuner may receive the broadcast content data, if the processor decidesto receive the broadcast content data.

Here, the application stores the filter code in the reception-sidebroadcast content provision apparatus or acquires the filter code fromthe network server of a broadcaster. Such operation may be performedthrough a WebSocket command and a control interface.

In one embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the processor may requestthe filter code from the application using a first API. Here, the firstAPI may correspond to the below-described Get Filter API.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the filter code may be avalue indicating a personalization category. In some embodiments, thefilter code may be determined by the broadcaster. For example, thefilter code may be given to a truck driver, a zip code, a gender, etc.according to a specific personalization category of the broadcaster. Thefilter code acquired from the network server of the broadcaster isrelated to the user of the reception-side broadcast content provisionapparatus and may be used to provide personalized broadcast content tothe user. In some embodiments, the filter code may be associated withbroadcast content data. The filter code associated with the broadcastcontent data may indicate a personalization description of the broadcastcontent data (file, etc.) The filter code may be unique in a range of anAppContext ID. In some embodiments, the filter code may be an unsignedinteger.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the processor may receivea JSON (JavaScript Object Notation) object from the application inresponse to the first API. In some embodiments, this JSON object mayinclude a pair of a filter code and expiration information. This filtercode may be given to the reception-side broadcast content provisionapparatus. In some embodiments, expiration information may indicate anexpiration time of the filter code or a valid period of the filter code.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the broadcast contentprovision apparatus may further include a storage. The above-describedprocessor may store the filter code acquired from the application in thestorage.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the application may usethe stored filter code regardless of communication with the networkserver of the broadcaster or whether the application is launched or not.For example, if the application is terminated and then is launched again(a user switches to another channel and returns to an original channel),it may be impossible to access broadband in order to acquire personalinformation through the network server of the broadcaster. Even in thiscase, the application may use the stored filter code to providepersonalized broadcast content.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the EFDT may be asignaling table for providing a description of files related to thebroadcast content data and/or NRT files. The EFDT may includeinformation on the files of the broadcast content and information ontransmission thereof. The EFDT may be one type of signaling information.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the EFDT may include afilter code associated with the broadcast content related file. Thisfilter code may be associated with the file and may be used to determinewhether the file is necessary to provide personalized broadcast contentand to determine whether the personalized broadcast content is receivedor not. In some embodiments, the EFDT may include a first filter codeassociated with a first file. Here, the first file may be one ofbroadcast content data. The first filter code may indicate apersonalization description of the first file.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the processor maydetermine that a related file is downloaded, if the filter code of theEFDT is equal to the stored filter code.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the tuner may selectivelydownload the file, if the processor determines that the file isdownloaded (received). In some embodiments, the tuner may receive thefile over a broadcast network. In some embodiments, the tuner mayreceive the file over a broadcast network using a NRT (Non-Real Time)method.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the tuner may furtherreceive a DWD (Distribution Window Description) as one of the signalinginformation. The processor may compare the filter code in the DWD withthe stored filter code to determine whether the broadcast content datarelated to the filter code in the DWD is received or not. The tuner mayreceive the broadcast content data, if the processor determines that thebroadcast content data is received.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the DWD may indicate timeintervals for transmitting one or more files. The DWD may be one ofsignaling mechanisms for notifying a receiver of when a specific type ofNRT data (file or media segment) will be delivered. The DWD may havefilter codes associated with files to be delivered in a distributionwindow. The DWD may include information on at least one distributionwindow. Here, the distribution window may mean a time interval scheduledto deliver broadcast content related files. The DWD may includeinformation on start and end times of the distribution window and filesdelivered in the distribution window. In addition, the DWD may includefilter codes for the files. The receiver may determine whether the givendistribution window is a window of interest using the filter codes fromthe viewpoint of personalization. Upon determining that a specific fileis necessary to provide the personalized broadcast content using thefilter codes and the distribution window information, the receiver mayaccess an appropriate broadcast stream at a file delivery time anddownload (receive) the corresponding file. The DWD may belong toapplication signaling.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the DWD may includeinformation indicating a distribution window in which a second file istransmitted and a second filter code. Here, the second file may be oneof the broadcast content related data. The second filter code may be afilter code indicating a personalization description of the second file.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the processor maydetermine that the related file is downloaded, if the filter code of theDWD is equal to the stored filter code.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the tuner may selectivelydownload the file, when the processor determines that the file isdownloaded (received). The processor may compare the second filter codein the DWD with the stored filter code to determine whether the secondfile is downloaded (received). In this case, the tuner may tune to anappropriate broadcast stream in the distribution window indicated by theDWD, thereby selectively receiving the second file. In some embodiments,the tuner may receive the file over the broadcast network. In someembodiments, the tuner may receive the file over the broadcast networkusing the NRT method.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the broadcast contentprovision apparatus may perform the selective downloading process evenwhen the application does not operate. For example, the broadcastcontent provision apparatus may perform the above-described selectivedownloading process even in a standby mode during a time correspondingto the distribution window.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the application may enablethe broadcast content provision apparatus to store the filter code usingthe second API. The second API may correspond to the below-described SetFilter API.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the second API may includea parameter having a second object. The second object may include a pairof a filter code and expiration information. In some embodiments,expiration information may indicate an expiration time of the filtercode or a valid period of the filter code.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the above-described firstAPI may be used for the broadcast content provision apparatus to acquirethe filter code from the application. The first API may be issued by thebroadcast content provision apparatus.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, the above-described secondAPI may be used for the application to set or store the filter code inthe broadcast content provision apparatus. The second API may be issuedby the application.

In another embodiment of the reception-side broadcast content provisionapparatus according to the present invention, after the reception-sidebroadcast content provision apparatus receives a specific file based ona specific filter code, if the application provides a new filter codeset excluding the specific filter code using a Set Filter API, thereception-side broadcast content provision apparatus may delete thespecific file.

In the reception-side broadcast content provision apparatus according tothe present invention and the embodiments thereof, the broadcast contentprovision apparatus may determine which filter code is applicable to theuser of the reception side to provide personalized broadcast content.

In the reception-side broadcast content provision apparatus according tothe present invention and the embodiments thereof, the broadcast contentprovision apparatus may suppress unnecessary data from occupying thememory through selective data reception.

The above-described embodiments of the reception-side broadcast contentprovision apparatus according to the present invention may be combined.In addition, the internal components of the reception-side broadcastcontent provision apparatus according to the present invention may beadded, changed, replaced or deleted according to embodiment. Inaddition, the above-described internal components may be implemented byhardware components.

FIG. 12 is a diagram showing a transmission-side broadcast contentprovision apparatus according to another aspect of the presentinvention.

According to another aspect, the present invention may be related to thetransmission-side broadcast content provision apparatus. Thetransmission-side broadcast content provision apparatus may supportpersonalized broadcast content provision using the filter code. Thetransmission-side broadcast content provision apparatus may be atransmission-side apparatus corresponding to the above-describedreception-side broadcast content provision apparatus.

Specifically, the transmission-side broadcast content provisionapparatus may generate broadcast content, generate a filter code for thebroadcast content data, generate an EFDT including the filter code, andtransmit the broadcast content data and the EFDT over a broadcastnetwork. Meanwhile, a filter code capable of being specified in areceiver may be generated and transmitted to an application in thereceiver over broadband.

The transmission-side broadcast content provision apparatus according tothe present invention may include a processor, a broadcast receiverand/or a network interface.

The processor may generate broadcast content data for providingbroadcast content. In addition, the processor may generate a filter codefor the broadcast content data. This filter code was described above. Inaddition, the processor may generate an EFDT. The EFDT may include adescription of the broadcast content data, that is, a file, and a filtercode for the file. In addition, the processor may generate a filter codecapable of being specified in a receiver.

The broadcast transmitter may transmit signaling information such as thegenerated broadcast content data and/or the EFDT over a broadcastnetwork.

The network interface may transmit the filter code capable of beingspecified in the receiver to the application of the receiver overbroadband.

The transmission-side broadcast content provision apparatus according tothe present invention may have embodiments corresponding to theabove-described reception-side broadcast content provision apparatusaccording to the present invention. The transmission-side broadcastcontent provision apparatus according to the present invention and theinternal components thereof may perform the embodiments corresponding tothe embodiments of the above-described reception-side broadcast contentprovision apparatus according to the present invention.

The above-described embodiments of the transmission-side broadcastcontent provision apparatus according to the present invention may becombined. In addition, the internal components of the transmission-sidebroadcast content provision apparatus according to the present inventionmay be added, changed, replaced or deleted according to embodiment. Inaddition, the above-described internal components may be implemented byhardware components.

FIG. 13 is a diagram showing an embodiment of a Get Filter API accordingto the present invention.

The Get Filter API according to the present invention may be used forthe reception-side broadcast content provision apparatus to acquirefilter information to filter information from an application. Thereception-side broadcast content provision apparatus may issue the GetFilter API to request the filter code from the application (broadcasterapplication). The application may send a response to the Get Filter APIto the reception-side broadcast content provision apparatus. Asdescribed above, the filter code may be used to determine which file isreceived (downloaded) in place of the application.

In one embodiment of the shown Get Filter API, the Get Filter API(t13010) may be defined as “org.atsc.getFilters”. Here, parameters maybe omitted. The response to the Get Filter API (t13020) may include aJSON (JavaScript Object Notation) object. This JSON object may include apair of key/value. Specifically, the JSON object may include a pair of afilter code and expiration information.

Specifically, the JSON object may include “type” and “properties”elements. Here, the “type” element may indicate that the JSON object isof an “object” type. The “properties” element may describe theproperties of the JSON object.

The “properties” element may include “filters” and/or “required”elements. The “filters” element may include filtering relatedinformation. The “required” element may indicate that thebelow-described “filterCode” element is a mandatory element.

The “filters” element may include a “type” element indicating that theelement is of an “array” type and an “items” element including filteringrelated information.

The “items” element may include a “filterCode” element and/or an“expires” element. These two elements may form a pair.

The “filterCode” element may indicate the above-described filter code.This element may be of an “integer” type. In some embodiments, thefilter code may be of an unsigned integer type as described above.

The “expires” element may indicate the above-described expirationinformation. This element may be of a “string” type. This expirationinformation may be represented in a dateTime XML data type defined inXSD Datatypes. The expiration information of this element may indicatean expiration time of the filter code indicated by the “filterCode”element. After the expiration time, the filter code may not be used.

In another embodiment of the Get Filter API, the “expires” element maybe omitted. In this case, the filter code indicated by the “filterCode”element may have an indefinite lifetime without expiration.

In another embodiment of the Get Filter API, the “expires” element is amandatory element and may always be present to form a pair with the“filterCode” element. In this case, the “required” element may indicatethat the “filterCode” element and the “expires” element are mandatoryelements.

In another embodiment of the Get Filter API, the “filters” element maybe indicated in a list of unsigned integers separated into a whitespace. At this time, each unsigned integer value may mean a filter code.In some embodiments, the filter codes may be associated with thebroadcast content data transmitted through the distribution window. Inthis case, the “filters” element may be of a “string” type.

In another embodiment of the Get Filter API, the “expires” element maybe represented in the format of a full 64-bit NTP (Network TimeProtocol) timestamp.

In another embodiment of the Get Filter API, the “expires” element mayfurther include a “format” element. The “format” element may indicatethe format of the expiration information of the “expires” element. Forexample, the “format” element may indicate that the expirationinformation has a format of “date-time”.

In the embodiments of the reception-side broadcast content provisionapparatus according to the present invention, the Get Filter API may bethe Get Filter API according to the above-described embodiments.

FIG. 14 is a diagram showing an example of using a Get Filter APIaccording to the present invention.

In the example of using the shown Get Filter API, the reception-sidebroadcast content provision apparatus may issue a Get Filter API(t14010). To this end, the reception-side broadcast content provisionapparatus may request the filter code from the application. This GetFilter API may have a value of “method” of “org.atsc.getFilters” and an“id” value of 57.

In the example of using the shown Get Filter API, the application maysend a JSON object in response to the Get Filter API. This JSON objectmay include a total of three pieces of filter information.

First filter information may indicate that the filter code is 101(“filterCode”: 101) and the filter code expires Jul. 17, 2016, at09:30:47 (“expires”: 2016-07-17T09:30:47). Second filter information mayindicate that the filter code is 102 (“filterCode”: 102) and the filtercode expires Jul. 17, 2016, at 09:30:47 (“expires”:2016-07-17T09:30:47). Third filter information may indicate that thefilter code is 103 (“filterCode”: 103) and the expiration time of thefilter code is not decided. In addition, the JSON object may have an“id” value of 57.

FIG. 15 is a diagram showing an embodiment of a Set Filter API accordingto the present invention.

The Set Filter API according to the present invention may be used forthe application to store the filter code in the reception-side broadcastcontent provision apparatus. The application launched in thereception-side broadcast content provision apparatus may issue a SetFilter API. To this end, the application may enable the reception-sidebroadcast content provision apparatus to store a specific filter code.As described above, the reception-side broadcast content provisionapparatus may selectively download an NRT data file using this filtercode. In this process, the stored filter code and the filter codeassociated with the broadcast content data in the EFDT and DWD may becompared with each other.

The Set Filter API may establish a set of filter codes. In this process,previous filter code setting may be cancelled. Here, a cookie, aseparate storage, etc. may be used to maintain the filter codes for thereception-side broadcast content provision apparatus.

In one embodiment of the shown Set Filter API, the Set Filter API may bedefined as “org.atsc.setFilters”. The Set Filter API may further includea parameter.

The parameter may include a “type” element and/or a “properties”element. The “type” element may indicate that the parameter is of an“object” type. The “properties” element may indicate the properties ofthe parameter.

The “properties” element may include a “filters” element and/or a“required” element. The “filters” element may include filter-relatedinformation. The “required” element may indicate that thebelow-described “filterCode” element is a mandatory element.

The “filters” element may include a “type” element and/or an “items”element. The “type” element may indicate that the “filters” element isof an “array” type. The “items” element may include a filter code and/orexpiration information.

The “items” element may include a “filterCode” element and/or an“expires” element.

The “filterCode” element may indicate the above-described filter code.This element may be of an “integer” type. In some embodiments, thefilter code may be of an unsigned integer type as described above. Here,the broadcaster may maintain uniqueness of the filter code in a range ofAppContextID.

The “expires” element may indicate the above-described expirationinformation. This element may be of a “string” type. This expirationinformation may be represented in a dateTime XML data type defined inXSD Datatypes. The expiration information of this element may indicatethe expiration time of the filter code indicated by the “filterCode”element. After the expiration time, the filter code may not be used.

In another embodiment of the Set Filter API, the “expires” element maybe omitted. In this case, the filter code indicated by the “filterCode”element may have indefinite lifetime without expiration.

In another embodiment of the Set Filter API, the “expires” element is amandatory element and may always be present to form a pair with the“filterCode” element. In this case, the “required” element may indicatethat the “filterCode” element and the “expires” element are mandatoryelements.

In another embodiment of the Set Filter API, the reception-sidebroadcast content provision apparatus may not use application filtercode information delivered through the Set Filter API.

In another embodiment of the Set Filter API, the “filters” element maybe indicated in a list of unsigned integers separated into a whitespace. At this time, each unsigned integer value may mean a filter code.In some embodiments, the filter codes may be associated with thebroadcast content data transmitted through the distribution window. Inthis case, the “filters” element may be of a “string” type.

In another embodiment of the Set Filter API, the “expires” element maybe represented in the format of a full 64-bit NTP (Network TimeProtocol) timestamp.

In another embodiment of the Set Filter API, the application may provideall filter codes to the reception-side broadcast content provisionapparatus. The application cannot determine how long the reception-sidebroadcast content provision apparatus maintains the filter code.Accordingly, all filter codes may be delivered through the Set FilterAPI. In this case, the filter codes delivered through the Set Filter APImay replace pre-stored filter codes.

In another embodiment of the Set Filter API, the application may providea null filter code to delete all the filter codes stored in thereception-side broadcast content provision apparatus.

In another embodiment of the Set Filter API, the “expires” element mayfurther include a “format” element. The “format” element may indicatethe format of the expiration information of the “expires” element. Forexample, the “format” element may indicate that the expirationinformation has a format of “date-time”.

In the embodiments of the reception-side broadcast content provisionapparatus according to the present invention, the Set Filter API may bethe Set Filter API according to the above-described embodiments.

FIG. 16 is a diagram showing an example of using the Set Filter APIaccording to the present invention.

In the example of using the shown Set Filter API, the application mayissue the Set Filter API to provide a total of three pieces of filterinformation to the reception-side broadcast content provision apparatus(t16010).

First filter information may indicate that the filter code is 101(“filterCode”: 101) and the filter code expires Jul. 17, 2016, at09:30:47 (“expires”: 2016-07-17T09:30:47a). Second filter informationmay indicate that the filter code is 102 (“filterCode”: 102) and thefilter code expires Jul. 17, 2016, at 09:30:47 (“expires”:2016-07-17T09:30:47). Third filter information may indicate that thefilter code is 103 (“filterCode”: 103) and the expiration time of thefilter code is not decided. In addition, the Set Filter API may have an“id” value of 57.

In the example of using the shown Set Filter API, the reception-sidebroadcast content provision apparatus sends a response (t16020). Thisresponse may have a null “result” and have an “id” value of 57.

FIG. 17 is a diagram showing an embodiment of a DWD according to thepresent invention.

The DWD according to the present invention may indicate a time intervalscheduled to transmit one or more files (distribution window). The DWDmay have filter codes associated with files to be delivered in thedistribution window.

In one embodiment of the shown DWD, the DWD may include one or moreDistributionWindow elements. One DistributionWindow element may indicateone distribution window. Files related to the broadcast content data maybe transmitted through the distribution window. More specifically, thefiles may be transmitted through an LCT channel indicated by thebelow-described @lctTSIRef attribute.

The @appContentLabel attribute may indicate a label for the files to bedelivered through the distribution window.

The @startTime attribute may indicate a start time of a time intervalindicated by the distribution window. The @endTime attribute mayindicate an end time of a time interval indicated by the distributionwindow.

The @lctTSIRef attribute may indicate an LCT channel which is a path fortransmitting the files delivered in the distribution window. Thisattribute may be the TSI (Transport Session Identifier) value of the LCTchannel.

The AppContextId element may indicate an Application Context ID. TheApplication Context ID may be a URI indicating an application resourceto be commonly used between a plurality of applications. TheAppContextId element may include an @dwFilterCode attribute.

The @dwFilterCode attribute may indicate the filter codes for thebroadcast content data transmitted through the distribution window. Thisattribute may be a list of the values indicating the filter codesseparated into a space. The filter codes may be unique in an ApplicationContext ID range of an AppContextId element.

Using the DWD and the filter codes in the DWD, it is possible todetermine with which filter codes the broadcast content data to bedelivered through the distribution window is associated. Using this, thereception-side broadcast content provision apparatus may determinewhether specific broadcast content data is suitable for provision ofpersonalized broadcast content and, if suitable, determine which LCTchannel is accessed in which distribution window (time interval) inorder to receive this broadcast content data.

FIG. 18 is a diagram showing another embodiment of the DWD according tothe present invention.

In another embodiment of the shown DWD, the @appContentLabel may have avalue of 10, the @startTime may have a value of 1488248597, and the@endTime may have a value of 1488255797. In this case, the distributionwindow indicated by the DWD may be a time interval starting at1488248597 and ending at 1488255797.

In addition, in another embodiment of the shown DWD, the AppContextIDelement may include an @dwFilterCode attribute and an @dwFCexpiresattribute. The @dwFilterCode attribute may has a value of “101 201 315”,which may indicate that the broadcast content data delivered through thedistribution window have filter codes of 101, 201 and 315. The@dwFCexpires attribute may include expiration information of the filtercodes. The expiration information may indicate a time when the filtercodes expire.

In another embodiment of the shown DWD, the reception-side broadcastcontent provision apparatus may store a filter code of 101. Since thisreception-side broadcast content provision apparatus transmits broadcastcontent data having a matching filter code in the distribution window,the file may be downloaded in the distribution window. However, if thereception-side broadcast content provision apparatus stores a filtercode of 314, since there is no matching filter code, no file may bedownloaded in the distribution window.

In the embodiments of the reception-side broadcast content provisionapparatus according to the present invention, the DWD may be the DWDaccording to the above-described embodiments.

FIG. 19 is a diagram showing a method of providing broadcast content ata reception side in a reception-side broadcast content provisionapparatus according to the present invention.

The method of providing the broadcast content at the reception side mayinclude requesting a filter code from an application using a first API,receiving a JSON object from the application in response to the firstAPI, storing the filter code, receiving an EFDT and/or comparing thestored filter code with the filter code of the EFDT to selectivelydownload a file.

The processor of the reception-side broadcast content provisionapparatus may issue the first API to request the filter code from theapplication launched in the apparatus. The filter code may be anunsigned integer and may be associated with a personalized categorydetermined by the broadcaster.

The processor may receive a JSON object from the application in responseto the first API. The JSON object may include a pair of the filter codeand expiration information indicating the expiration time of the filtercode.

The processor may store the filter code in a storage.

A tuner may receive an EFDT. The EFDT may include a first filter codeassociated with a first file. The first filter code may indicate apersonalization description of the first file.

The processor may compare the stored filter code with the first filtercode in the EFDT to determine whether the first file is downloaded ornot. The tuner may selectively download the first file according todecision of the processor.

In another embodiment of the method of providing broadcast content at areception side, the tuner may receive a DWD. The DWD may includeinformation on a distribution window, through which a second file isdelivered. In addition, the DWD may include a second filter codeassociated with the second file. At this time, the processor may comparethe stored filter code with the second filter code in the DWD todetermine whether the second file is downloaded or not. Upon determiningthat the second file is downloaded, the tuner may selectively downloadthe second file through the distribution window indicated by the DWD.

In another embodiment of the method of providing broadcast content at areception side, the application may use a second API to store the filtercode in the reception-side broadcast content provision apparatus. Thesecond API may include a parameter having a second object. The secondobject may include a pair of a filter code and expiration informationindicating the expiration time of the filter code.

In another embodiment of the method of providing broadcast content at areception side, the first API may be issued by the reception-sidebroadcast content provision apparatus and may be used to acquire thefilter code from the application.

In another embodiment of the method of providing broadcast content at areception side, the second API may be issued by the application and maybe used to set the filter code in the reception-side broadcast contentprovision apparatus.

A method of providing broadcast content at a transmission side in atransmission-side broadcast content provision apparatus according to thepresent invention may have the embodiments corresponding to the methodof providing the broadcast content at the reception side according tothe present invention. The transmission-side broadcast content provisionapparatus according to the present invention and the internal componentsthereof may perform the embodiments corresponding to the method ofproviding the broadcast content at the reception side according to thepresent invention.

Modules or units may correspond to processors that execute continuousprocesses stored in a memory (or a storage unit). The respective stepsdescribed in the above-described embodiments may be performed byhardware/processors. The respective modules/blocks/units described inthe above embodiments may operate as hardware/processors. In addition,the methods proposed in the present invention may be executed as codes.These codes may be written in a processor-readable storage medium, andthus may be read by a processor provided by an apparatus.

Even though the respective drawings have been separately described forconvenience of description, embodiments described in the respectivedrawings may be merged into a new embodiment. In addition, designing ofa computer-readable recording medium in which a program for executingthe above-described embodiments according to necessity of a personskilled in the art is within the scope of the present invention.

Referring to the apparatuses and methods according to the presentinvention, configurations and methods of the embodiments are notrestrictively applicable, and all or some of the above-describedembodiments may be selectively combined and configured such that theembodiments can be variously changed

Meanwhile, the methods proposed in the present invention may beimplemented as processor-readable code stored in a processor-readablerecording medium included in a network device. The processor-readablerecording medium includes all types of recording devices in whichprocessor-readable data is stored. Examples of the processor-readablerecording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, afloppy disk, an optical data storage device, etc. In addition, theexamples include a carrier-wave type implementation such as atransmission over the Internet. Furthermore, as the processor-readablerecording medium is distributed to a computer system connected via anetwork, processor-readable code can be saved and executed in adistributed manner.

Further, even though preferred embodiments of the present invention havebeen illustrated and described, the present invention is not restrictedto a certain embodiment described above, and various modifications andvariations can be made by those skilled in the art without departingfrom the subject matter of the present invention as defined by theclaims. Furthermore, these modified embodiments should not be understoodseparately from the spirit or scope of the present invention.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both the apparatus and method inventions may becomplementarily applicable to each other.

It should be understood by those skilled in the art that various changesand modifications can be made in the present invention within the spiritor scope of the present invention. Therefore, the present invention isintended to include changes and modifications of the present inventionwithin the scope of accompanying claims and equivalents thereof.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both the apparatus and method inventions may becomplementarily applicable to each other.

MODE FOR INVENTION

Various embodiments have been described in best modes.

INDUSTRIAL APPLICABILITY

The present invention is used in a series of broadcast signal provisionfields.

It is clear to those skilled in the art that various changes andmodifications can be made in the present invention within the spirit orscope of the present invention. Therefore, the present invention isintended to include changes and modifications of the present inventionwithin the scope of accompanying claims and equivalents thereof.

The invention claimed is:
 1. A method for providing a broadcast contentin an apparatus, the method comprising: requesting a filter code to anapplication running on the apparatus by using an Application ProgrammingInterface (API), wherein the filter code is an integer associated withpersonalization categories as determined by a broadcaster; receiving aJavaScript Object Notation (JSON) object from the application inresponse to the API, wherein the JSON object includes the filter codeand expiration information indicating an expiry of the filter code;storing the filter code; receiving a Distribution Window Description(DWD) including information for indicating a distribution window duringwhich a first file will be delivered and a first filter code associatedwith the first file, wherein the first filter code represents apersonalization description for the first file; and selectivelydownloading the first file during the distribution window by comparingthe stored filter code with the first filter code in the DWD.
 2. Themethod of claim 1, wherein the API is one of Websocket interfaces forcommand and control.
 3. The method of claim 1, further comprising:receiving an Extended File Delivery Table (EFDT) having a second filtercode associated with a second file, wherein the second filter coderepresents a personalization description for the second file; andselectively downloading the second file by comparing the stored filtercode with the second filter code in the EFDT.
 4. The method of claim 1,wherein the filter code is created by the broadcaster according to aparticular personalization category of the broadcaster.
 5. The method ofclaim 4, wherein the particular personalization category of thebroadcaster is a truck owner, a sustaining member, or a zip code.
 6. Anapparatus for providing a broadcast content, comprising: a storage; aprocessor configured to request a filter code to an application runningon the apparatus by using an Application Programming Interface (API),wherein the filter code is an unsigned integer associated withpersonalization categories as determined by a broadcaster, wherein theprocessor is further configured to receive a JavaScript Object Notation(JSON) object from the application in response to the API, wherein theJSON object includes the filter code and expiration information forindicating an expiry of the filter code, and wherein the processor isfurther configured to store the filter code in the storage; and a tunerconfigured to receive a Distribution Window Description (DWD) includinginformation for indicating a distribution window during which a firstfile will be delivered and a first filter code associated with the firstfile, wherein the first filter code represents a personalizationdescription for the first file, and wherein the tuner is furtherconfigured to selectively download the first file during thedistribution window by comparing the stored filter code with the firstfilter code in the DWD.
 7. The apparatus of claim 6, wherein the API isone of Websocket interfaces for command and control.
 8. The apparatus ofclaim 6, wherein the tuner is further configured to receive an ExtendedFile Delivery Table (EFDT) having a second filter code associated with asecond file, wherein the second filter code represents a personalizationdescription for the second file, and wherein the tuner furtherconfigured to selectively download the second file by comparing thestored filter code with the second filter code in the EFDT.
 9. Theapparatus of claim 6, wherein the filter code is created by thebroadcaster according to a particular personalization category of thebroadcaster.
 10. The apparatus of claim 9, wherein the particularpersonalization category of the broadcaster is a truck owner, asustaining member, or a zip code.